Application adaptive mobile terminal

ABSTRACT

A user interface is presented for mobile devices that provides for efficient and logical movement between applications on the mobile device. Multiple applications may be used simultaneously and interactively. Such uses and data are stored on the device and re-presented to the user at subsequent uses to provide efficiencies in commonly used functions, applications, and contacts.

This U.S. Utility patent application claims priority to U.S. ProvisionalPatent Application Ser. No. 60/751,210, filed Dec. 19, 2005, the contentof which is hereby incorporated by reference in its entirety into thisdisclosure.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to wireless communication. Moreparticularly, the present invention relates to wireless communicationdevices and services with multi-operational user interfaces.

2. Background of the Invention

Conventional service environments in use today applied to mobilenetworked devices are typically cumbersome and inefficient. Users haveno choice but to learn the functions associated with every applicationavailable on the mobile device without regard to their own specificneeds or relation to their own specific context. In essence, users haveto conform to the limitations and style of the particular mobile deviceand its pre-set menu of applications. Furthermore, the manner ofaccessing the various pre-set programs and applications on a particularmobile device are cumbersome and inefficient. “Drill down” menu-drivenapplication interfaces are one such manner, and are archaic andnon-intuitive. Users have to sift through multiple level menus to find aparticular program or application, and then activate that particularapplication to perform a desired function. Often times, the processitself required for use or activation of certain applications is thebiggest obstacle for a user because of its non-intuitive or cumbersomenature. Thus, a user may not ever access or utilize a particularapplication on a mobile device solely because that application isdifficult to access on that device.

Thus, a need exists in the art of mobile device access user interfacesfor creating an efficient, intuitive, and easy to use and understandinterface that allows the user to have access to one or moreapplications quickly and simultaneously, as well as toggle between suchmultiple applications at will with minimal effort.

SUMMARY OF THE INVENTION

The present invention provides in exemplary embodiments a novel userinterface environment for allowing the user easy, efficient andintuitive access to multiple applications on a mobile device in a quickand logical manner. This system provides for a simple, easy to useinterface, while applying a higher level of intelligence which users cantake advantage of without being encumbered by the complexity of the vastamount of information being exchanged. Such a novel user interfacechanges the way that users access and utilize one or multipleapplications on a given mobile device.

In one exemplary embodiment, the present invention is a user interfacefor a mobile device. The interface includes a virtual template area; anobject positioned in a particular spot in the virtual template area; anda screening window that traverses across the virtual template area;wherein when the screening window is positioned on the object in thevirtual template area, the object function may be activated.

In another exemplary embodiment, the present invention is a mobiledevice. The device includes a virtual template area; an objectpositioned in a particular spot in the virtual template area; and ascreening window that traverses across the virtual template area;wherein when the screening window is positioned on the object in thevirtual template area, the object function may be activated.

In yet another exemplary embodiment, the present invention is a mobiledevice. The device includes a handset; a virtual template area on thehandset; an object positioned in the virtual template area; and ascreening window on the handset that traverses across the virtualtemplate area; wherein when the screening window is positioned on theobject in the virtual template area, the object function may beactivated by a user of the handset.

In one particular exemplary embodiment, the invention provides aGraphical User Interface (GUI) with a unique look and feel for amulti-tasking multi-applications environment used in mobile networkingterminals.

In another exemplary embodiment, the invention provides an intelligentinteractive information repository scheme used in mobile devices for thecollection of data/information and subsequent user profiling at thedevice level.

In yet another exemplary embodiment, the invention provides a uniquehuman interface scheme for mobile devices utilizing the combination ofvirtual space, object oriented operating environment and visuallyoriented input functions.

In another exemplary embodiment, the invention provides a schema forproviding a Service Oriented Architecture (SOA) utilizing serviceabstraction from the application layer through the GUI to the Signalingprotocol, gaining and storing information in the interaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B show a device and mechanical user interface according toan exemplary embodiment of the present invention.

FIG. 2 shows a “Virtual” Template Area according to an exemplaryembodiment of the present invention.

FIG. 3 shows the transition from a Launching Platform to VirtualTemplate State according to an exemplary embodiment of the presentinvention.

FIG. 4 shows screen movement in virtual space according to an exemplaryembodiment of the present invention.

FIG. 5 shows on the fly navigation utilizing a zoom function accordingto an exemplary embodiment of the present invention.

FIG. 6 shows on the fly application to application transition accordingto an exemplary embodiment of the present invention.

FIG. 7 shows multi-application function according to an exemplaryembodiment of the present invention.

FIG. 8 shows a diagram of a services abstraction framework according toan exemplary embodiment of the present invention.

FIG. 9 shows an object/service interaction according to an exemplaryembodiment of the present invention.

FIG. 10 shows an intelligent repository architecture according to anexemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a more robust, more intelligent and moreversatile system for cellular, wireless devices, Wi-Fi and wirelinenetworks than is conventionally available. Through the use of thepresent invention, a user may operate multiple applications, present onthe cellular/wireless device, simultaneously and interactively,regardless of what device is used or what network delivers it. Suchability has not been possible in conventional devices because of theconventional configurations that such devices are made available in andthe lack of ability to access and utilize multiple applications.Furthermore, the interactivity of applications, as shown and presentedin the present disclosure, is unavailable to the level and capabilitypresented herein.

The present invention departs from traditional User Interfaces (UI) andthe associated arcane logic, an environment which has traditionallyaddressed the needs of the conventional mobile network user and isdefined by three basic elements. The Adaptive User Interface (AUI) isthe first of these. By expanding the visual plane of the device andcreating a simple human interface, the present invention provides mobiledevices with much more user friendly properties and can be adapted tothe demands of the user. This approach is contrary to current designphilosophy which is predicated on a single application use model wherethe mobile subscriber is given a fixed set of features and functionsthrough a predefined applications set. Each application utilizes its ownUser Interface and there is no commonality in the structure of theapplication or its concern for interaction with other applications.

A second element of the present invention that is distinguishable fromconventional systems is the interactive approach of modelingapplications around the design of an Object Oriented Operating (OOO)environment where objects are created, acted upon and change behaviorbased upon usage, input and interaction from other objects. Thisnecessitates the common design philosophy of (seemingly) disparateapplications in order for the user to dictate usage and not be confinedto a predetermined set of rules.

Finally, in order to create a dynamic profile of usage based on patternsof behavior, a mechanism is built to take advantage of input from theuser, from outside sources such as applications servers and from othermechanisms such as intelligent signaling protocols such as SessionInitiation Protocol (SIP). An Intelligent Information CollectionRepository (IICR) on the mobile device is used to enhance this novelmethodology.

In considering the abilities of the present invention, it's useful toconsider examples of exemplary human interfaces that may be usedaccording to the present invention. One such example is device 100 asshown in FIG. 1. The Adaptive User Interface 101 is predicated on theuse of an Object Oriented Operating environment. Use of this technologyis useful in the development and deployment of an architecture thatprovides the proper level of consistency and security over mobilenetworks. The Human Interface is defined by a combination ofinteractions between the software enabling the objects acted upon andthe “mechanical input”101, 111, 199 from the user at the device. In thiscase, as represented by FIGS. 1A and 1B, a bezel 101 and button 111, 199configuration is used as an example of the mechanical input. Othervariations of this example may be incorporated. For example, the buttons102, 103, 104, 105, 106, 107, 108, 109, 100 on the bezel may bepositioned elsewhere. Also, other user interfaces may be used, such as atactile user interface, where the user pushes the screen directly forparticular movement or function. Adoption of this principle may also bebased on a softkey implementation.

As an example, considering the mechanical bezel 101 more closely, asshow in FIG. 1B, a useful aspect of this implementation is a simpleuser-feedback-response that requires a minimum amount of intervention onthe part of the user to access/act upon “objects” (defined in moredetail below) or applications. The look and feel consists of thespecific elements pertaining to the Virtual Template described in moredetail in FIG. 2 and subsequent interfaces with the acted upon objects.The exemplary elements used here include HOME, UP 103, DOWN 107, ZOOM IN102, ZOOM OUT 108, RIGHT 110, LEFT 104, BACK 105, FORWARD 109, GO, ARROWINPUT 106, SWITCH 199 and HOT KEYS 111 (Pre Load). This look and feelcan be further grouped into the following; Movement/Motion Navigationand Action Navigation. The HOME function can be the only exception tothis description in that it functions both in Movement/Motion andAction.

The HOME key may be an exemplary human input key that is defined asalways either Universal HOME 222 or an Object HOME, as set by the user.State 1 is the condition for Universal HOME 222 as depicted by thevirtual template area 200 shown in FIG. 2. After input is received forthis state, the view shown is the Universal HOME 222 mode. In State 2,when applied to any object, it is the home (or Initiation) of thatobject. For instance, when an object 221 defined as an application islaunched, it may have a variety of children objects spawned or exposelower level features/functions. Object HOME is not necessarily screendependent. For instance, a “Map” object could be launched and therelated Object HOME could be defined by the starting place on the map.Invoking Object HOME in this case would return the user to the firstinstance or placement on the map display. In State 2, when input fromthe Home key is taken, the object will revert back to its original (orParent) state (see FIG. 9 for a depiction of this environment). Methodsother than a physical key may be used as long as the input resultsfunction in the way described here.

As used above and throughout this disclosure, an “object” 221 is asoftware bundle of variables and related methods. Objects 221 are key tounderstanding object-oriented technology. There are many examples ofreal-world objects: one's pet, one's desk, one's television set, one'sbicycle. These real-world objects share two characteristics: they allhave state and behavior. For example, dogs have state (name, color,breed, hungry) and behavior (barking, fetching, and wagging tail).Bicycles have state (current gear, current pedal cadence, two wheels,number of gears) and behavior (braking, accelerating, slowing down,changing gears). Software objects are modeled after real-world objectsin that they too have state and behavior. A software object maintainsits state in one or more variables. A variable is an item of data namedby an identifier. A software object implements its behavior withmethods. A method is a function (subroutine) associated with an object(from The Java Tutorial, Sun Microsystems, copyright 1995-2005).

As briefly alluded to above, and shown in FIG. 2, a display mappingtemplate 220 may be used to facilitate the movement 230 between objects221. In order to maximize the volume of object choices available on amobile device, a virtual space 200 is created to display multipleapplications and provide increased visibility and choice once theapplications are launched. In FIG. 2, the applications are representedby blocks labeled OBJECT. Reducing the size of the visual imagery to thephysical limitations of the device 212 display real estate 213 is notalways the optimum solution. This mechanism provides for increasedvisibility without having to overly modify the original content. Theoption is still available to limit the total display space of theindividual application to the physical display size 213. However, thevirtual template area 200 is still available outside of the framedefined by that application. In essence, the Virtual Template Area 200is an open screen on which multiple applications can reside, be launchedand interact with each other. Each object 221 in the defined VirtualTemplate space can be displayed and acted upon. Universal HOME 222 isthe initiation site for start up of the device. Universal HOME 222 isalso the reference point to which all operations begin. Objects otherthan the start up functions may not reside in Universal HOME space.

As shown in the example of FIG. 2, the HOME location 222 is positionedin the lower right hand corner of the Virtual Template Area (VTA) 200 asan example. However, the HOME location 222 is not limited to suchposition and may be located elsewhere, such as in the center of the VTA200 to allow for better accessibility to the objects that will besurrounding the HOME area. Also, the user may choose the location of theHOME area depending on the user's desire for the position of particularobjects about the HOME.

The initiation of an action to be taken with object/application ispredicated on its placement in the device “field of view” (specificallyin the HOT SPOT, see FIG. 3 and on for a description and definition) andthen performing the appropriate object characteristic (launch, view,message, etc).

The Primary State Human Interface will now be described in more detailwith respect to FIG. 3. The Adaptive User Interface 300 is defined by aconsistent first level “field of view” 340. The first level field ofview will consist of the Push Me (virtual) button which launches theoriginating service architecture and enables the object field to beloaded and accessed. The object field is defined by mapping objects tothe virtual template 341 (defined in FIG. 2 and following). Thisoriginal field of view 340 is known as Universal HOME. Within the centerarea of the screen a “Hot Spot” is defined. This area is THE launchingpoint of any object. When an object crosses into the Hot Spot zone, itcan be acted upon. Highlighting of the object shall be done whenever itis within this area. The user has the option to act on the object bytouching it on the screen or using the function GO. Various physicalelements 301, 310, 311 of the device as shown before 312 and after 314movement into a hot spot area are similar to those shown in priorfigures and examples.

Movement/Motion Navigation (Right/Left, Up/Down, Diagonal) provides forvisual modification of an object, as shown in device 400 in FIG. 4. Thedescriptions of some of these exemplary functions are provided in moredetail below.

UP/DOWN: In state 1 this interface function will scroll up or downutilizing the Virtual Template Area (see FIG. 2). In state 2 (after aninitial object has been acted upon) the subject of the object can bescrolled up or down.

RIGHT/LEFT: In state 1 this interface function will scroll right or leftutilizing the Virtual Template Area (see FIG. 2). In state 2 (after aninitial object has been acted upon) the subject of the object can bescrolled right or left.

ARROW Functions: In state 1 this interface function will scrolldiagonally utilizing the Virtual Template Area (see FIG. 2). In state 2(after an initial object has been acted upon) the subject of the objectcan be scrolled diagonally.

In the examples shown in FIG. 4, a desired object 442 is moved to theright in the direction of the arrow 446 with respect to the physicalscreen area of the device 400 by movement into space 443. This may beperformed by pushing of the right/left arrow as desired. As anotherexample, object 444 may be moved horizontally in a southwest directionindicated by arrow 447 by pushing of the appropriate arrows on the bezelof the device 400. Countless other examples are possible and within thepurview of the present invention.

As shown in FIG. 5, Movement/Motion Navigation (zoom) provides for ZOOMIN/OUT: This interface function provides for magnification of, orzooming away from the object in the field of view. For example, a zoomin button 550 may be placed at the top of the device 500 to enable easyzoom of an object (such as a map) 551 to a second view 552 such that theoriginal object 551 has been enlarged 553 to show more detail. Theconverse may also be performed.

In another example of the abilities of the present invention, and asshown in FIG. 6, Action Navigation, unlike Movement/Motion Navigation,may be used as a controlling function. In this mode, an object 656within the Hot Spot zone of an equipped device 600 may be instructed toperform a task, change states or interact with another object. Thefollowing includes a description of some of these exemplary functions. Anon-limiting example may be the instant change 670 of the view of oneobject 656 (such as a map) to another object 657 (such as a videostream) by the pushing of a button 655 which may be positioned on alower end of the device 600. Many other non-limiting examples are alsopossible and within the purview of the present invention. These otherexamples include, for example, the below functions and abilities.

FWD/BACK: After an object has been acted upon, this function allows forthe navigation TO a previously selected object (FWD) or back to the lastobject acted on or command executed (BACK).

SWITCH: This function allows the user to switch betweenobjects/applications working/running but are not in the current field ofview.

GO: When an object is in the Hot Spot (see FIG. 3), the user has theoption to act on this object using the GO function.

TOUCH SCREEN: When an object is in the Hot Spot (see FIG. 3) the userhas the option to act on this object using the TOUCH SCREEN function.This function may be initiated by a tactile input to the display area.

HOT KEYS: This function allows the user to act upon pre-defined objectsthat are typically most used. When the function is enabled, apreconfigured object/application is launched. The user has thecapability to customize these keys for this purpose.

As shown by device 700 in FIG. 7, a Multi-Application, Multi ServiceEnvironment may be created by combining a variety of the above describedfunctions together, thereby creating a total user experience. Theability to “pop” navigation of objects/applications using variousbuttons or keys 760, 761, 762, 763 and “pop” betweenobjects/applications 764, 765, 766, 767, 768 allows the user theflexibility to rapidly access and act upon the information/communicationdesired based on any context/situation or scenario. Utilizing anintelligent interface also narrows the number of objects/applications toa customized user profile, thus creating a higher level of efficiency onthe device. This customized profile is discussed in more detail belowwith respect to Service Interaction and Intelligent RepositoryArchitecture.

FIG. 8 shows an exemplary Services Abstraction Framework 800 accordingto the present invention. As there are a variety of device hardwareplatforms and device operating systems and environments 876 using basicSIP stack 877, there is a need for a service abstraction architecturelayer 874 allowing for objects/applications 870, 871, 872 to operateubiquitously in the User Experience. This Service Oriented Architecture(SOA) 874 ties 898 the Adaptive User Interface 873 into service enablers875, 878, 879 for intelligent processing of data. In this example, theservice enablers 875, 878, 879 are identified as Presence 878,Availability 879 and Instant Messaging (IM) 875, although any genericservice enabler can be used in place of these. The information exchangedthrough the SOA enables interaction of the vast number ofobjects/applications available to the device and provides a means tochange the objects acted upon. These changes can be in state, behavioror new information development.

An example of Object/Service Interaction 900 is shown in FIG. 9. Objectscan be applications, data, or other forms of information/communication.Objects can act independently, in conjunction with other objects withintheir parent-child relationships or with other generically disassociatedobjects. In this figure, Object 1 981 has spawned children objects O1¹-O1 ³ 984, 985, 986, respectively. Interaction between these objects islinear and thus the information flows only between the correspondingelements (e.g., parent-child, child-parent). The same is true for Object2 982 in relation to O2 ¹. Note however the difference in the flow forObjects O2 ² 987 and O3 ¹ 988. A new level of exchange has taken placewith object O3 ¹ 988, between O2 ² 987 and Object 3 Parent 983. Theresulting action pertains to Object 1 Parent 981. The resultantinformation exchange from O2 ² 987 and O3 ¹ 988 is acted on Object 1Parent 981. This event results in new information which is collected inObject 1 981 and passed onto an Intelligent Information CollectionRepository (see discussion relating to FIG. 10). Objects may be actedupon by agents within the mobile device or from network elements such asthe signaling protocol or applications servers also exchangingdata/information.

FIG. 10 shows an exemplary Intelligent Repository Architecture 1000according to the present invention, with components similar to thoseshown in FIG. 8. As multiple objects/applications 1091 are acted upon,an Intelligence Information Collection Repository (IICR) 1090 isrequired at the mobile device. The net result is a user profile that isdynamically stored and fed back to the Adaptive User Interface VirtualTemplate 1092. These profiles can be visually represented at the VirtualTemplate Layer, Applications Layer or within the object itself. DynamicUser Profiles (DUP) may be defined by, but not limited to, the followingattributes: Type of Service, Most Often Used, Priority of Queuing,Object/Application Dependency (highest interaction between objects),Object Interactivity (Information tags stored as connection pointersfrom object-to-object), Date/Time of usage, and Enabler InformationTags. Thus, the user's behavior pattern and past use of function andcontacts have an impact on the applications that may be presented to theuser in future use of the device.

The foregoing disclosure of the preferred embodiments of the presentinvention has been presented for purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Many variations andmodifications of the embodiments described herein will be apparent toone of ordinary skill in the art in light of the above disclosure. Thescope of the invention is to be defined only by the claims appendedhereto, and by their equivalents.

Further, in describing representative embodiments of the presentinvention, the specification may have presented the method and/orprocess of the present invention as a particular sequence of steps.However, to the extent that the method or process does not rely on theparticular order of steps set forth herein, the method or process shouldnot be limited to the particular sequence of steps described. As one ofordinary skill in the art would appreciate, other sequences of steps maybe possible. Therefore, the particular order of the steps set forth inthe specification should not be construed as limitations on the claims.In addition, the claims directed to the method and/or process of thepresent invention should not be limited to the performance of theirsteps in the order written, and one skilled in the art can readilyappreciate that the sequences may be varied and still remain within thespirit and scope of the present invention.

1. A user interface for a mobile device, the user interface comprising:a virtual template area, the virtual template area including a regiondefined as a universal home, the universal home including a plurality ofstart-up objects; an object positioned in a particular spot in thevirtual template area, the object being a software bundle of variablesand related methods; and a screening window that traverses across thevirtual template area; wherein upon positioning the screening window onthe object in the virtual template area, the object may be activated;wherein the activated object spawns a second activated child object andcommunicates usage information to and receives usage information fromthe second activated child object, the second activated child objectinteracting with a plurality of child objects, the interaction resultingin new usage information that pertains to the activated object, whereinthe new usage information is transmitted to the activated object andstored in a user profile for a user, and wherein the mobile deviceincludes a home key set by the user as an object home for a user-definedstarting place on a map object, the home key returning the user to theuser-defined starting place on the map object upon being activated. 2.The interface of claim 1, further comprising a plurality of objectspositioned at various particular spots in the virtual template area. 3.The interface of claim 2, wherein at least two of the plurality ofobject functions are activated simultaneously.
 4. The interface of claim1, wherein the mobile device is a cellular telephone.
 5. A mobiledevice, comprising: a virtual template area, the virtual template areaincluding a region defined as a universal home, the universal homeincluding a plurality of start-up objects; a home key set by a user asan object home for a user-defined starting place on a map object, thehome key returning the user to the user-defined starting place on themap object upon being activated; an object positioned in a particularspot in the virtual template area; and a screening window that traversesacross the virtual template area; wherein upon positioning the screeningwindow on the object in the virtual template area, the object may beactivated; wherein the activated object spawns a second activated childobject and communicates usage information to and receives usageinformation from the second activated child object, the second activatedchild object interacting with a plurality of child objects, theinteraction resulting in new usage information that pertains to theactivated object, and wherein the new usage information is transmittedto the activated object and stored in a user profile for the user. 6.The device of claim 5, further comprising a plurality of objectspositioned at various particular spots in the virtual template area. 7.The device of claim 6, wherein at least two of the plurality of objectfunctions are activated simultaneously with the ability to interact withother activated objects.
 8. The device of claim 7, further comprising amechanical input receiver for the user to use to move the screeningwindow over an object.
 9. The device of claim 8, wherein the mechanicalinput receiver includes buttons on a bezel on the mobile device.
 10. Thedevice of claim 8, wherein the mechanical input receiver includestactile buttons on a screen on the mobile device.
 11. The device ofclaim 8, whereas the mechanical input receiver includes a set ofsoftware enabled hotkeys.
 12. The device of claim 5, further comprisingan information repository for collection of data from previous userinteractions and re-presentation of the collected data at subsequentinteractions.
 13. A mobile device, comprising: a handset; a virtualtemplate area on the handset, the virtual template area including aregion defined as a universal home, the universal home including aplurality of start-up objects; a home key set by a user as an objecthome for a user-defined starting place on a map object, the home keyreturning the user to the user-defined starting place on the map objectupon being activated; an object positioned in the virtual template area,the object being a software bundle of variables and related methods; anda screening window on the handset that traverses across the virtualtemplate area; wherein upon positioning the screening window on theobject in the virtual template area, the object may be activated by theuser; wherein the activated object spawns a second activated childobject and communicates usage information to and receives usageinformation from the second activated child object, the second activatedchild object interacting with a plurality of child objects, theinteraction resulting in new usage information that pertains to theactivated object, and wherein the new usage information is transmittedto the activated object and stored in a user profile for the user of theactivated object.
 14. The device of claim 13, further comprising aplurality of objects positioned at various particular spots in thevirtual template area.
 15. The device of claim 14, wherein at least twoof the plurality of object functions are activated simultaneously withthe ability to interact with other activated objects.
 16. The device ofclaim 15, further comprising a mechanical input receiver for the user touse to move the screening window over an object.
 17. The device of claim16, wherein the mechanical input receiver includes buttons on a bezel onthe mobile device.
 18. The device of claim 16, wherein the mechanicalinput receiver includes tactile buttons on a screen on the mobiledevice.
 19. The device of claim 16, whereas the mechanical inputreceiver includes a set of software enabled hotkeys.
 20. The device ofclaim 13, further comprising an information repository for collection ofdata from previous user interactions and re-presentation of thecollected data at subsequent interactions.